People Management Issues in Scrum from COBIT Perspective

Albeit Scrum teams have a freedom inside the team, they one way or another still have an interaction with the remaining parts of organizations which have authorities over the same subject which is maximizing the value. Scrum should gain recognition throughout the organization, and be applied appropriately. Otherwise, conserving and protecting the natural structure and mechanism of the teams becomes a challenge. The focus migrates from people centric management to product centric management by Scrum methods and the structure of Scrum shapes around the product concept. Line managers, who have primary responsibilities over people, disappear. However, still someone should watch over people who are prone to be forgotten somewhere in the product lines, aggressively designed for continuous and unremitting delivery. Accountabilities and responsibilities of people management functions of teams should be addressed in Scrum. As a part of it, responsibilities of workload and resource capacity management among and inside the Scrum teams should be defined. Performance measurement and reward systems must be suitably designed [4] team based, where collective goals supersede individual accomplishments [8]. Moreover, career path development is a field to study for Scrum which provides a flat structure of organization rather than a hierarchy including steps to managerial positions. For the teams that are expected to trust each other, the concept of codes of ethics plays a critical role for the success of agile methodologies. And, organizations should be aware of that it may take enormous effort, time, and patience to build a culture of trust and respect among the employees [4]. Documentation as useful artifacts for the backup of information is discouraged in Scrum [5]. Thus, much of the knowledge in agile development resides in the heads of the development team members [4]. Using an agile approach entails formidable responsibility on the client’s part [8]. The success of agile development relies on finding customers who are expected to be collaborative, representative, authorized, committed, and knowledgeable [3]. Great Scrum also needs great product owners [11]. Consequently, Scrum brings the advantages of flexibility and human initiative, yet opens gates to the diversity and unpredictability of people which at the end may inhibit to achieve a level of assurance and control [2], [6]. Thus, organizations within COBIT environments need to strike a balance between the two conflicting interests: agility and control.